Amount Verification

To help combat fraud, Segpay has introduced Amount Verification, in which you can require a consumer to verify his or her identity up front before purchasing your service or product. At signup, the consumer is initially directed to submit payment for a small, undisclosed amount, then asked to check his or her credit card statement for the amount and enter it on your site to complete verification.

Getting Set Up

If you want to set up Amount Verification, you need to contact techsupport@segpay.com to let us know. We need to approve your account for three items:

  1. Dynamic Pricing: Amount Verification requires setting up a Dynamic Price point, where you’ll specify a price range. Then, for each verification you will dynamically send Segpay the specific amount to charge, within that range.

  2. Pre-Auth Only: This ensures that your consumers are not actually billed for these verification charges. The authorizations will appear in their accounts but will be voided the next day.

  3. Merchant Services: If you don’t already have a User ID and Access Key for Segpay’s Merchant Services and/or Reporting Services (SRS), we will create one for you.

Once you have approval for these items, you can set up Amount Verification in the Segpay Merchant Portal by creating (or editing) a Dynamic Price Point and selecting Amount Verification:

See our Dynamic Pricing documentation which explains how to set up a Dynamic Price Point. You will specify a price range with minimum and maximum amounts that can be used for verification.

Add your new price point to one or more packages. Get your button code/Join Link, which will look something like this example:

Copy 
https://srs.segpay.com/MerchantServices/DynamicPricing/?merchantId=xxxxx&amount=1.85

However, the Join Link you will actually use for verification will require additional parameters, which are discussed below.

Getting the Dynamic Pricing ID

With each signup, you must make a request to Segpay’s Merchant Services, sending the amount to be charged, along with your Merchant ID, similar to the following example:

Copy 
https://srs.segpay.com/MerchantServices/DynamicPricing/?merchantId=xxxxx&amount=1.85

Note that Merchant Services uses basic authentication, so you will need your UserID and UserAccessKey to make this request.

Segpay will return a Pricing GUID, which you will append to the Join link to take the consumer to the payment page, as in this example:

http://secure2.segpay.com/billing/poset.cgi?x-eticketid=xxxxxx:yyyy&dynamicpricingid=251c80f7-7095-4a3f-9461-422c7821a9ba&dynamicdesc=JustTesting

The following parameters are all required along with your Join Link:

Parameter Definition
ETicketID Format XXXXXX:YYYYY, where XXXXXX=package ID and YYYYY=price point ID. Get these values from your Segpay rep, or in the Merchant Portal in the Packages area (Package ID) and Price Points area (Price Point ID).
DynamicDesc A description of the transaction, to be displayed on the payment page and the email receipt and shared with our support reps to help them assist customers. This string should be URL encoded, as in this example: Video+Bundle+for+2+Movies+Movie1+and+Movie2
DynamicPricingID The pricing GUID value that is returned when you make the request to Segpay and send the amount to be charged for verification. This ID is used to charge the correct amount to the consumer. Note: If you use Dynamic Multicurrency, we will charge the amount in the consumer’s local currency (if different than the base currency in your price point). For example, if the original base amount is 1.85 USD and the consumer’s local currency is NOK, the amount billed will be 16.03 NOK (subject, of course, to the USD-NOK exchange rate is on the day of the transaction).

Unlike conventional Dynamic Pricing, the consumer won’t see the verification amount anywhere on the pay page, not even in the page source. He or she must get the amount from their credit card account in order to verify themselves.

All other system and user-defined variables can be appended to the Join link as well. For more information about passing and returning data, see our Processing API for Merchants article. (See section titled, “Pre-populate Fields or Request Data”).

Postback Data

Make sure you include the following two parameters in your Transaction postback notification URLs:

Parameter Definition
<Authprice> Converted amount of the transaction, according to your base currency and the exchange rate on the day of the transaction.
<Authcurrency> Currency used for the transaction, based on the consumer’s selection.

Getting those two items ensures that you can verify the consumer whether he or she enters the amount on your site in the base or converted currency. Using the example in the DynamicPricingID definition above, the consumer can verify by entering 1.85 (USD) or 16.03 (NOK).